Capturing consumer preferences as requirements for software product lines

Using i* to Capture Consumer Preferences as Requirements for Software Product Lines

The need for software to fit to diversity of numerous consumers has become a norm. Furthermore, technology innovations stimulate the growth of such software, thus making it even more available and appealing to consumers. Although how economic values relate and influence IT systems is an area that has been addressed, it is not clear whether and how consumer values do so. To address this challeng...

Capturing Architectural Knowledge of Software Product Lines

Context. In the context of software product lines, architectural decisions determine the design of an architecture that provides the software with the ability to be configured for different product variants and extended to accommodate future requirements. Although, variability models describe the different configurations of current and future products that the product line supports, the knowled...

Requirements Engineering for Software Product Lines

The cost of fixing a requirements defect later in the development stage is much higher than the cost of identifying and fixing it in the early stages of development. In order to do this the system requirements must be properly identified, analyzed and reviewed early in the development process. Requirements engineering is such a process that focuses on discovering, analyzing, documenting and man...

Goals and Scenarios for Requirements Engineering of Software Product Lines

Goal-oriented requirements engineering (GORE) approaches offer a natural way to capture similarities and the variability in software product lines (SPLs) development. Besides, they can effectively capture both the stakeholders’ objectives and the system requirements. From i* models, for example, it is possible to systematically obtain feature models. To complement the requirements specification...

Requirements engineering for systems and software product lines